I have seen numerous questions and answers, but nothing that makes my XP show up in Network on W7. I have since a long time created a shortcut to "\\XP\SHARENAME", and when I click this shortcut, the explorer window opens and shows the files and folders in that share. This means that the workgroup name is the same on both computers, that the firewalls on both computers let through whatever protocols are required for this to work. In "Printers and Units" on the W7, the XP printer is listed. In sharing center on the W7, I click "See the whole network" (I am translating back from Norwegian; the standard English wording may be different) and get "Network map", "Windows finds no computers or units". The Network and Sharing Center window shows the W7, the wireless network, and the internet. I click the network, and I get a window showing a list of computers (one computer, the W7), a list of media units (three W7 user names), and a list of "network infrastructure" (one item, the label of the wireless router). I notice that some write about LLTD responder for XP. I downloaded the responder installer to the XP SP3 computer, and ran it. It says the system is newer than the update and I do not need the update. When I click "See the whole network" I see in the Wireshark capture a dozen LLTD ethernet packets both on the W7 and on the XP. They are all broadcasts from the W7, there seems to be no response. I guess I have to activate the responder somehow. I also guess I may have to tweak Norton Antivirus' firewall somehow, but I cannot find a way to specify non-IP protocols. I have tried to set the network type to home and to work. I do not notice any difference. Are there any further firewall ports I need to open? What else? I also have problems with accessing the XP printer from the W7. While the printer itself shows, nothing actually appears on the printer or in the printer queue on either machine. Wireshark captures show such an overwhelming amount of traffic that I give up finding out what it all is - at least until somebody points me to a manageable source of information about the protocols. I wonder if the problem could be related to the difference in processors. The W7 is a 64-bit AMD, while the XP is a 32-bit Intel. Do I have to do something special to get a 64-bit driver for the printer? It is a HP Photosmart C5380 AllInOne. Clicking "properties" on the printer icon on the W7, shows it is a HP, and that it is a printer and scanner, but it does not show the model. Does that indicate something? Thanks

To unpack the Responder installer - hmmm... the only way I know of, since it's self unpacking and executing, is to try to install it and when it errors don't close it. Instead, find the temp folder where it unpacked and copy the structure and files to a different folder, then let it close. That's what I had to do to install it manually on Windows 2003 Server. You haven't really been using TCP/IP printing even though you've been printing over a TCP/IP network. To make this work, in XP you need to first turn it on: Start->Control Panel->Add or Remove Programs->Add/Remove Windows Components. Scroll down the list until you see Other Network File and Print Services and turn it on. In Windows 7 it's Start Orb->Control Panel->Programs and Features->Turn Windows features on or off. Scroll down the list and find Print and Document Services expand it and check the boxes that say LPD Print Service and LPR Print Monitor. You'll also need to open up TCP port 515 in the firewalls on both machines, both incoming and outgoing. To set up the printer you'll need the print driver for 64-bit Windows 7 from HP: http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=3765673 (this the English driver for the 5324, but it should still work.) Once you have that and have it all unzipped somewhere - Start Orb->Control Panel->Devices and Printers->Add a printer. Select Add a local printer then Create a new port. Pull down the list and select LPR port. Click Next. When it asks for Name or address of server providing lpd enter the name or IP address of your XP machine. For Name of printer or print queue on that server enter the printer's share name. Click OK. From this point on it's the same as adding any other printer. Select your driver and follow the prompts. Good luck.

You've got several things going on here and it's difficult to determine exactly what your problem/question is, so forgive me if I get something wrong. 1. The XP machine doesn't show up on the Windows 7 Network Map. You're right, you need to install the LLTD Responder on the XP machine for this to work. For it work with SP3 you'll need to request the Hotfix: http://support.microsoft.com/kb/922120. But the XP machine should still show up when you expand the Network tree in the left panel of any Explorer window. This has nothing to do with the Network Map. 2. Can't print from Windows 7 64-bit to a shared printer on 32-bit XP. There's been numerous threads on this and lots of solutions. The one I've found that works best for me is to install the printer as a local device using one of the TCP/IP printing methods - either the one built in to Windows or the UNIX LPD/LPR protocol. That way you don't have to mess around with trying to get 64-bit drivers loaded onto a 32-bit box. The fact that the model of printer doesn't show up when you view its properties means nothing, you probably have the HP Universal or some other generic drivers installed.

I just rebooted, and now the XP (and the Linux laptop) show when I expand the network, as you say. I can only think of three things to attribute this change to, first that I selected network type "workplace" (don't know the standard English name, I am translating from Norwegian; work as opposed to home or public networks); I turned off ipv6 (another suggestion in the threads) and I installed an update that was waiting for a reboot. (Sigh, why must I reboot before anything takes effect?) As to the LLTD responder XP SP3 hotfix 922120, it appears it is not available in Norwegian edition. Since the English edition of the responder installer refuses to install I suspect the same thing will happen to the hotfix. Yet I saw somebody wrote I could unpack the responder installer and run the the relevant file on the command line, that would install it. So I may try this later tonight, when my girlfriend allows. But how do I unpack it...? I just tested the printer. The document appears in the printer queue on the W7, and remains there. Hm, local printer using TCP/IP printing method, Windows builtin ? What is that? Isn't that what I have been using all the time? (except it is remote, not local. Local tcp/ip?) Another change, before rebooting I tried also to export a share, but got an error message when setting permissions for everyone. Now it appears to work... but it never completes (the mouse cursor has a little circle chasing its own tail), and the list of users turns into the numerical form S-1-5-18, etc. Thanks

To unpack the Responder installer - hmmm... the only way I know of, since it's self unpacking and executing, is to try to install it and when it errors don't close it. Instead, find the temp folder where it unpacked and copy the structure and files to a different folder, then let it close. That's what I had to do to install it manually on Windows 2003 Server. You haven't really been using TCP/IP printing even though you've been printing over a TCP/IP network. To make this work, in XP you need to first turn it on: Start->Control Panel->Add or Remove Programs->Add/Remove Windows Components. Scroll down the list until you see Other Network File and Print Services and turn it on. In Windows 7 it's Start Orb->Control Panel->Programs and Features->Turn Windows features on or off. Scroll down the list and find Print and Document Services expand it and check the boxes that say LPD Print Service and LPR Print Monitor. You'll also need to open up TCP port 515 in the firewalls on both machines, both incoming and outgoing. To set up the printer you'll need the print driver for 64-bit Windows 7 from HP: http://h10025.www1.hp.com/ewfrf/wc/softwareCategory?os=4063&lc=en&cc=us&dlc=en&sw_lang=&product=3765673 (this the English driver for the 5324, but it should still work.) Once you have that and have it all unzipped somewhere - Start Orb->Control Panel->Devices and Printers->Add a printer. Select Add a local printer then Create a new port. Pull down the list and select LPR port. Click Next. When it asks for Name or address of server providing lpd enter the name or IP address of your XP machine. For Name of printer or print queue on that server enter the printer's share name. Click OK. From this point on it the same as adding any other printer. Select your driver and follow the prompts. Good luck.

You are fantastic! I just started the download of the printer driver. I thought it may be useful for somebody to know how the non-tcp/ip printing (What is it called?) is failing. When I print something here on the W7, the XP pops up a message: Microsoft Visual C++ Runtime Library Runtime Error! Program: C:\WINDOWS\system32\spoolsv.exe This application has requested the Runtime to terminate in an unusual way. Please contact the application's support team for more information. I cannot try the tcp/ip method until tomorrow because the XP is now being used by a fellow for something urgent. Thanks

I just tried the tcp/ip (really lpr/lpd) method of printing, and I got a beautiful test page. I also found the way of installing the lltd responder in this link: http://x3webworx.wordpress.com/2008/05/27/link-layer-topology-discovery-kb922120-not-included-in-sp3-no-problem-read-on/ In short, run the installer with an option: -x:c:\mytempfolder This unpacks the contents of the downloaded file into the specified directory. Then enter the subfolder Sp2qfe. Copy the following files to the corresponding folders: ip\rspndr.inf c:\windows\inf rspndr.exe c:\windows\system32 rspndr.sys c:\windows\system32\drivers. Finally, run rspndr.exe -i. Thanks!